-
-
Notifications
You must be signed in to change notification settings - Fork 616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix incorrect design of handlers (Frequency, RunningAverage, etc.) #1567
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks @sdesrozis !
@sdesrozis thanks for the update! I was thinking as Checkpoint and ModelCheckpoint fix is the most simple and we do not break other things, it would be better to do it in a separate PR. For others, I'm not yet sure about the fix to adopt. |
Ok so if I understand correctly, I do a new PR with last commits about ModelCheckpoint fix, right ? And let's see for others ? |
Exactly! |
To be honest currently I'm not that sure about introducing things in this way. Let's try to find a better design that you already told previously about... I'd prefer to keep things as is instead of introducing a half-good solution. What do you think ? |
Not relevant at the moment. I prefer close this PR. |
Fixes #1405
Description:
Frequency
: introduction of a specific usageFrequencyWise
to fit theMetric.attach()
api.Check list: